-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(v2): autoprefix css #1605
feat(v2): autoprefix css #1605
Conversation
* misc(v2): clean up work * misc(v2): rename components
* feat(v2): implement component overriding * siteDir theme overriding should work for > 1 level directory * fallback for essential component like Loading * rename default -> classic
* feat(v2): easier plugin theme components override * add context * refactor again * rename eject -> swizzle * nits
* feat(v2): Algolia search plugin * patch PR facebook#1440 (facebook#1441) * alternative implementation * typo * refactor noop * rename SearchAlgolia -> SearchBar * changes.md
…k#1442) * refactor(v2): move headerLinks -> themeConfig & rm dead code * rm -rf dead code
* chore(v2): add flow setup * nits * fix * add flow-typed * ignore compiled library * fix error * fix typing * fix module name mapper * setup for @docusaurus/core * dont try remove type without @flow * fix can't find @docusaurus/utils * fix test * remove obscure relative paths * more refactoring * add typing for server/load/theme.js * no need to ship .flow source
* feat(v2): meta description * add description for blog as well * fix non-descriptive text link * remove font awesome * switch front-matter -> gray-matter
* refactor(v2): blog data revamp * fix(v2): fix incorrect blog total count * misc: remove console.log * feat(v2): export frontMatter as an object within MDX file (facebook#1451) * refactor. Don't confuse metadata & frontmatter * export frontMatter in content itself * nits * nits name * dont truncate first four lines in blog
* feat(v2): blog tags * feat(v2): blog tags
* fix: right TOC should not strip special chars * nits
* fix(v2): handle non existent blog, docs, pages * nits
* feat(v2): list blog tags on posts * fix date handling on blog header * fix console log error due to non unique key
Deploy preview for docusaurus-2 ready! Built with commit b708cb7 |
Deploy preview for docusaurus-preview ready! Built with commit 5763760 |
Deploy preview for docusaurus-preview ready! Built with commit b708cb7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the attempt :)
- When using postcss-loader in webpack with css-loader, u need to set importLoader in css-loader. Try to read more on css-loader as well
- for browserslist, user doesnt always have the configuration. Sometimes everyone want to compile to all browser, did you make sure it works and has a default ?
- Please provide a test plan that makes sure it fixes the problem, what kind of difference adding this postcss loader add. “Run automated test cases” as a test plan isn’t a good practice.
- While CRA config can be taken as inspiration, CRA is not server side rendered. Did you make sure it works on SSR. ?
CRA also doesnt allow customizing postcss options (which made people had to create CRA-rewired and all hacky tools out there) or they had to eject.
Can we do this for docusaurus without ejecting ?
5. Do we really need stage 3 feature and postcss-flexbugs-fixes ?
This is a good start, thank you
Please provide a strong test plan,
@endiliey Thanks for your support. I will read about all the things you mentioned. And do the necessary changes. If needed I will ask you for help. Thanks |
@endiliey Updated the pull request
|
i'd go for it because autoprefixing css counts as a chore that people will most likely have to deal with or may not even be aware that their projects already have it set up |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pls rebase or merge conflict
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Thanks a lot @shakcho Sorry for the delay, was sick |
Motivation
Automatically add vendor prefix for CSS
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
In the root directory execute the following command
go to http://localhost:3000/docs/introduction
Open chrome devtools, we should see the position sticky should get vendor prefixed with
-webkit-sticky to work on Safari Browser as shown in the image below.
Try the URL in Safari browser, now the left sidebar should not scroll while scrolling.
Related PRs
I'm not aware of any